Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Fix error with large size initialisation in nocomp mode #1072

Merged
merged 3 commits into from
Sep 29, 2023

Conversation

JessicaNeedham
Copy link
Contributor

Fixes #1071. Initialisation by dbh was failing in no comp mode because height was not being initialised. This PR adds a call to h_allom so that trees can be demoted in canopy_structure if site spread has been updated in the first time step.

Collaborators:

Expectation of Answer Changes:

nocomop initialisation by dbh should now run, rather than result in an error.

Checklist:

  • My change requires a change to the documentation.
  • I have updated the in-code documentation .AND. (the technical note .OR. the wiki) accordingly.
  • [ x] I have read the CONTRIBUTING document.
  • FATES PASS/FAIL regression tests were run
  • If answers were expected to change, evaluation was performed and provided

Test Results:

CTSM (or) E3SM (specify which) test hash-tag:

CTSM (or) E3SM (specify which) baseline hash-tag:

FATES baseline hash-tag:

Test Output:

Compiles and runs on Perlmutter with https://github.com/glemieux/E3SM/tree/lnd/fates-refactor E3SM branch and latest FATES commit.

Add a call to h_allom so that trees can be demoted in
canopy_structure
@glemieux glemieux self-assigned this Aug 28, 2023
@rgknox rgknox self-requested a review September 11, 2023 23:40
Copy link
Contributor

@rgknox rgknox left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Looks good, makes sense.

Stretch goal: In the call to create_cohort, we've already updated that named argument to convey a zero aged cohort. How about that integer value of 1 that we pass. I think it is canopy layer. Perhaps we should use a named constant there too. Actually, I'm surprised we pass anything in, we shouldn't be defining the layer upon create cohort, that is an emergent phenomonena. It almost seems better to pass nothing and set it to uninitialized. I'll make an issue instead.

@rgknox
Copy link
Contributor

rgknox commented Sep 11, 2023

Here is the new issue: #1082
So my suggestion of changing canopy layer to the create_patch call is out of scope and I see nothing else to do on this PR.

@rgknox
Copy link
Contributor

rgknox commented Sep 29, 2023

running tests: /glade/scratch/rgknox/tests_0928-180603ch

tests pass, merging

@rgknox rgknox merged commit 21e18c6 into NGEET:main Sep 29, 2023
@JessicaNeedham JessicaNeedham deleted the jfn-nocomplargetreeinitfix branch January 11, 2024 23:18
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

nocomp large tree initialisation failing
3 participants